Text message generation for emergency services as a backup to voice communications

ABSTRACT

A mobile device may detect when a calling party dials an emergency service to request emergency assistance. Following input of the dialed digits, the device may automatically generate a text message in addition to initiating a voice call, both of which may be transmitted over a wireless data network. The wireless network may correlate the two calls as originating from the same emergency situation and may attempt to deliver the two calls to a Public Services Answering Position (PSAP) at an appropriate emergency center. If the PSAP does not receive a voice call, the PSAP may communicate with the device via test messaging.

CROSS REFERENCE TO RELATED APPLICATIONS

The instant application is a continuation of, and claims priority to,U.S. patent application Ser. No. 13/689,396, filed Nov. 29, 2012. U.S.patent application Ser. No. 13/689,396 is incorporated by referenceherein in its entirety.

TECHNICAL FIELD

The technical field generally relates to wireless communications, andmore specifically relates to text messaging and emergency voice calls,and even more specifically relates to text message backup for emergencyvoice calls.

BACKGROUND

Mobile devices, such as mobile phones, for example, may be used as alink to emergency services. In isolated or rural areas, a mobile phonemay be the only link to emergency services. Many factors may influencethe ability to make an emergency call. For example, battery power of amobile phone may be low, the propagation path between a cellular towerand a mobile phone may have poor propagation characteristics, and/orobstructions may exist in a propagation path. Such factors may prevent acall for emergency services.

SUMMARY

The following presents a simplified summary that describes some aspectsor embodiments of the subject disclosure. This summary is not anextensive overview of the disclosure. Indeed, additional or alternativeembodiments of the subject disclosure may be available beyond thosedescribed in the summary.

A text message for emergency services may be generated as a backup to anemergency voice call (e.g., a 911 voice call). For example, when a userof a mobile device dials 9-1-1 to request emergency assistance, thedevice may automatically generate a text message in addition toinitiating a voice call. In various example embodiments, the textmessage may be generated when the device in not able to initiate and/orestablish the voice call. For example insufficient signal strength mayprevent the device from initiating and/or establishing a voice call.Insufficient signal strength may be a result of any appropriate factoror factors, such as, for example, battery power of the device may below, a propagation path between a cellular tower and the device may havepoor propagation characteristics, and/or an obstruction or obstructionsmay exist in a propagation path.

In an example embodiment, if a voice call cannot be initiated and/orestablished, a text message may be sent instead of the voice call. Inanother example embodiment, a text message and a voice call may be sentconcurrently.

For example, the device may be capable of determining when an emergencycall is being initiated (e.g., dialing 9-1-1). Upon determining that theemergency call is being initiated (e.g., detection of dialed digits),the device may automatically generate a text message. The text messagemay be generated in addition to the voice call. The text message and thevoice call may be transmitted over a wireless data network. The wirelessnetwork may correlate the text message and the voice call as originatingfrom the same emergency situation and deliver them to an appropriatePublic Services Answering Position (PSAP) in an appropriate emergencycenter. If the voice call is received by the emergency center, a voiceconversation may ensue. If no voice call is received at the emergencycenter, a text messaging session may ensue.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference is made here to the accompanying drawings, which are notnecessarily drawn to scale.

FIG. 1 is a flow diagram of an example process for text messagegeneration for emergency services as a backup to voice communications.

FIG. 2 illustrates an example system and process for text messagegeneration for emergency services as a backup to voice communications.

FIG. 3 is a block diagram of an example communications device configuredto facilitate text message generation for emergency services as a backupto voice communications.

FIG. 4 is a block diagram of an example network entity for text messagegeneration for emergency services as a backup to voice communications.

FIG. 5 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network, withinwhich text message generation for emergency services as a backup tovoice communications may be implemented.

FIG. 6 illustrates an architecture of a typical GPRS network withinwhich text message generation for emergency services as a backup tovoice communications can be implemented.

FIG. 7 illustrates an example block diagram view of a GSM/GPRS/IPmultimedia network architecture within which text message generation foremergency services as a backup to voice communications may beimplemented.

FIG. 8 illustrates a PLMN block diagram view of an example architecturein which text message generation for emergency services as a backup tovoice communications may be incorporated.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Aspects of the instant disclosure are described more fully herein withreference to the accompanying drawings, in which example embodiments areshown. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide anunderstanding of the various embodiments. However, the instantdisclosure may be embodied in many different forms and should not beconstrued as limited to the example embodiments set forth herein. Likenumbers refer to like elements throughout.

For many people, mobile devices, such as mobile phones for example, maybe more than a mere vehicle for communication. The devices may serve asa lifeline to emergency services. This especially may be true inisolated or rural areas. Signal strength, however, may be insufficientto initiate, establish, and/or maintain a voice connection. This maybecome critical in emergency situations, for example, wherein anindividual may be trying to contact a 911 emergency center forassistance.

A complete lack of signal may prevent a device from sending and/orreceiving both voice and text messages. It may be possible however, tosend a text message when conditions prevent sending and/or receivingvoice messages. And it may be possible to maintain a text messagingsession when a voice session may be dropped. This may be due to a textmessage requiring less bandwidth than a voice session, text messagetermination after the message is sent, or any appropriate combinationthereof. Thus, for example, if a connection is intermittent, a textmessage may be able to be sent to its intended recipient, and a voicecall may be interrupted and/or dropped.

Therefore, it may be advantageous for a mobile device to automaticallygenerate a text message associated with every 911 call attempt and forthe telecommunications network to correlate both forms of communicationfrom call origination to the terminating emergency center. In caseswhere the voice call is successful, the text message can be discarded.However, in those cases where the voice call is unsuccessful due toinsufficient signal strength, the text message can provide a channel ofcommunication between the caller and the emergency center. In some casesthe caller might not be aware that a text message was sent and received;however, information on location could be used by authorities forfurther investigation. In some cases, this could be a matter of life ordeath.

FIG. 1 is a flow diagram of an example process for text messagegeneration for emergency services as a backup to voice communications. Acall may be initiated at step 12. The call may be, for example, a callfor emergency services, a 9-1-1 call, a call to a relative, or anyappropriate call. A text message may be generated at step 14. In anexample embodiment, the text message may be automatically generated. Thetext message may be automatically generated when the call is initiated.In an example embodiment, the text message may be automaticallygenerated when it is determined that the call is of a predetermined typeor class, such as, for example, an emergency call. An emergency call maycomprise a 9-1-1 call (e.g., called number is 9-1-1), a call to apredetermined number, a call to a number that is determined to berelated to an emergency call, or the like, or any appropriatecombination thereof. Predetermined numbers may comprise, for example, alist of predetermined phone numbers such as a phone number of a firedepartment, a phone number of an ambulance, a phone number of a policestation, a phone number of a hospital, a phone number of a relative(e.g., parent, child, etc.), or the like. In an example embodiment, whenthe call is initiated, at step 12, the list of predetermined numbers maybe compared to the number being called, and if a match exists, it may bedetermined that the call is an emergency call.

In an example embodiment, when the call is initiated (at step 12), thenumber being called may be used to query a database, a search engine,memory, or the like to determine if the number is associated with anemergency call. For example, the number may be used to search adirectory to determine to whom the number is assigned. If the number isassigned to a hospital, a police station, an ambulance service, etc.,the call may be determined to be an emergency call.

The text message may comprise any appropriate message. The text messagemay be predetermined, generated dynamically when the call is initiated,or any appropriate combination thereof. For example, the text messagemay comprise a predetermined message such as, for example, “Help,” “NeedAssistance,” etc. The predetermined text message may include the name ofthe person sending the message. The name of the person may be obtained,for example, from profile information stored on a mobile device fromwhich the text message is being generated, the mobile device may beprogrammed to store a subscriber's name, for incorporation into the textmessage, or any appropriate combination thereof. Accordingly, thepredetermined message may comprise a message such as, for example,“Help, my name is Joe Smith,” “Need Assistance, my name is Joe Smith”etc.

The text message may comprise information that is determined dynamicallyas triggered by initiation of the call. For example, the text messagemay comprise location information, time, etc. In an example embodiment,the text message may comprise a current location of the mobile devicegenerating the text message, the most recent known location of themobile device generating the text message, or the like, or anyappropriate combination thereof. The text message may comprise a time atwhich the text message is being generated. Location information may beformatted in any appropriate manner, such as, for example, latitude,longitude, map coordinates, addresses, etc. In an example embodiment,location information may be formatted in accordance with geographic codereferences such as the Federal Information Processing Standard (FIPS),ZIP codes, and/or the National Weather Service Specific Area MessageEncoder (SAME) codes, Geographic Information System (GIS) Alert MappingService, or the like, or any appropriate combination thereof.

In an example embodiment, when the call is initiated (at step 12), aprompt may be rendered on the mobile device from which the call is beinginitiated. The prompt may be provided in any appropriate manner, suchas, for example, visually, audibly, mechanically (e.g., vibration), orthe like, or any appropriate combination thereof. The prompt mayindicate that a user of the mobile device should speak into the device.The prompt may indicate that the user should speak his/her name,location, and/or nature of the emergency. For example, upon determiningthat the call is an emergency call, a message may be displayed on themobile device indicating that the user should say his/her name,location, and nature of the emergency. The audio information spoken bythe user may be converted into text. The converted text may beincorporated into the text message generated at step 14.

Text messaging may be initiated and a voice call may be initiated atstep 16. Text messaging and the voice call may be initiated in anyappropriate manner, such as, for example, a text messaging session and avoice call session may be initiated via communication with anappropriate entity of a network. As described in more detail herein, thenetwork may comprise any appropriate communications network and theentity (or entities) may comprise any appropriate entity (or entities)of the communications network.

At step 18, the text messaging session and the voice call session may bemarked, or tagged, to indicate commonality. The text messaging sessionand the voice call session may be marked, or tagged, in any appropriatemanner. For example, information in each of the text messaging sessionand the voice call session may be formatted to include an indication ofthe mobile device from which the sessions are being established, anindication of a subscriber associated with the mobile device, anidentification number indicated that the text messaging session and thevoice call session are correlated or paired, or the like, or anyappropriate combination thereof.

It may be determined if conditions are sufficient to establish and/ormaintain a voice call at step 20. Conditions, or factors, to beconsidered may include signal strength, battery power of the mobiledevice, propagation characteristics, obstructions, or the like, or anyappropriate combination thereof. In an example embodiment, a signalreceived by the mobile device may be analyzed (e.g., signal strength,power, voltage, current, etc.). If it is determined that the receivedsignal strength is less than a threshold value, it may be determinedthat conditions are not sufficient to establish and/or maintain a voicecall session. If it is determined that the received signal strength isequal to or greater than a threshold value, it may be determined thatconditions are sufficient to establish and/or maintain a voice callsession. The threshold value may comprise any appropriate value, suchas, for example, a value of power, a value of voltage, a value ofcurrent, a percentage value of power, a percentage value of voltage, apercentage value of current, or the like, or any appropriate combinationthereof. In an example embodiment, the mobile device may measure signalstrength and may adjust power as needed to support communications.

If is determined, at step 20, that conditions are not sufficient toestablish and/or maintain a voice call session, it may be determined atstep 22 if conditions are sufficient for text messaging at step 22.Conditions, or factors, to be considered may include signal strength,battery power of the mobile device, propagation characteristics,obstructions, or the like, or any appropriate combination thereof. In anexample embodiment, signal strength (e.g., power, voltage, current,etc.) of a signal received by the mobile device may be analyzed. If itis determined that the received signal strength is less than a thresholdvalue, it may be determined that conditions are not sufficient toestablish and/or maintain a text call session. If it is determined thatthe received signal strength is equal to or greater than a thresholdvalue, it may be determined that conditions are sufficient to establishand/or maintain a text call session. The threshold value may compriseany appropriate value, such as, for example, a value of power, a valueof voltage, a value of current, a percentage value of power, apercentage value of voltage, a percentage value of current, or the like,or any appropriate combination thereof.

If is determined, at step 22, that conditions are not sufficient toestablish and/or maintain a text messaging session, the process mayproceed to step 16 to try again.

If is determined, at step 20, that conditions are sufficient toestablish and/or maintain a voice call session, the voice call may beforwarded at step 28. The voice call may be forwarded via anyappropriate network, such as, for example, a voice network, a networkcapable of communicating voice, or any appropriate combination thereof.Optionally, if is determined, at step 20, that conditions are sufficientto establish and/or maintain a voice call session, the voice call andthe text message may be forwarded at step 30. The voice call may beforwarded via any appropriate network and the text message may beforwarded via any appropriate network. For example, the voice call maybe forwarded via a voice network, a network capable of communicatingvoice, or any appropriate combination thereof. The text message may beforwarded via a data network, a network capable of communicating data, anetwork capable of communicating text, or any appropriate combinationthereof. In an example embodiment, the text message may be forwarded viaa network capable of communications via the short messaging service(SMS) system.

If is determined, at step 22, that conditions are sufficient toestablish and/or maintain a text messaging session, the text message maybe forwarded at step 24. The text message may be forwarded via anyappropriate network, such as, for example, a data network, a networkcapable of communicating text, or any appropriate combination thereof.The text message may be forwarded via a data network, a network capableof communicating data, a network capable of communicating text, or anyappropriate combination thereof. In an example embodiment, the textmessage may be forwarded via a network capable of communications via theshort messaging service (SMS) system.

A communication may be received step 26. For example, signaling toestablish a voice call session may be received at step 26, a textmessage may be received at step 26, or both signaling to establish avoice call session and a text message may be received at step 26.

It may be determined, at step 32 if the received communication is a textmessage, signaling to establish a voice call session, or both a textmessage and signaling to establish a voice call session. If the receivedcommunication is a text message, communication may be conducted with themobile device via text messaging, at step 34. If the receivedcommunication is signaling to establish a voice call session,communication may be conducted with the mobile device via voice, at step36. If the received communication comprises signaling to establish avoice call session and a text message, communication may be conductedwith the mobile device via voice, at step 38. Optionally, communicationmay be conducted with the mobile device via voice and text at step 38.

Communications may be conducted between the mobile device and anappropriate entity, such as, for example, a public safety answeringpoint (PSAP), a police station, a fire department, an ambulance service,a relative, etc. In an example embodiment, if the voice called isdropped, lost, or becomes intermittent (step 40), the communication maybe switched over to a text communication (step 34). In an exampleembodiment, a PSAP may have the ability to launch a text message to themobile device, which may be activated after trying to re-establish avoice call. To achieve this, the PSAP may initiate a message in aSession Initiation Protocol (SIP) session for example. TheNext-Generation Emergency Services IP-Network (ESI-Net) Selective Routermay retain information related to which Text Gateway server the originaltext message was forwarded from. The session may then be establishedthrough that Gateway to the wireless network and the calling party. Ifthe call is not dropped, not lost, or does not become intermittent (step32), the call may continue to be monitored as depicted at step 40.

FIG. 2 illustrates an example system and process for text messagegeneration for emergency services as a backup to voice communications.As depicted in FIG. 2, a user (e.g., subscriber) 42, may initiate anemergency call, for example (e.g., to 9-1-1, to hospital, to police, tofire department, to relative, to designated number, etc.). An emergencycall may include any appropriate emergency call as described herein. Theuser 42 may initiate the call via a mobile device 44, to a mobiletelephone switching office 48, via a wireless network 46, at steps 62and 64. The call can be in the form of any appropriate call as describedherein. The call may be, for example, a call for emergency services, a9-1-1 call, a call to a relative, or any appropriate call. The mobiledevice 44 may generate a text message. In an example embodiment, thetext message may be automatically generated by the mobile device 44. Thetext message may be automatically generated when the call is initiated.In an example embodiment, the text message may be automaticallygenerated when it is determined that the call is of a predetermined typeor class, such as, for example, an emergency call. An emergency call maycomprise a 9-1-1 call (e.g., called number is 9-1-1), a call to apredetermined number, a call to a number that is determined to berelated to an emergency call, or the like, or any appropriatecombination thereof. Predetermined numbers may comprise, for example, alist of predetermined phone numbers such as a phone number of a firedepartment, a phone number of an ambulance, a phone number of a policestation, a phone number of a hospital, a phone number of a relative(e.g., parent, child, etc.), or the like. In an example embodiment, whenthe call is initiated, the list of predetermined numbers may be comparedto the number being called, and if a match exists, it may be determinedthat the call is an emergency call.

In an example embodiment, when the call is initiated, the number beingcalled may be used to query a database, a search engine, memory (e.g.,on the device 44), or the like to determine if the number is associatedwith an emergency call. For example, the number may be used to search adirectory to determine to whom the number is assigned. If the number isassigned to a hospital, a police station, an ambulance service, etc.,the call may be determined to be an emergency call.

The text message may comprise any appropriate message. The text messagemay comprise a short messaging service (SMS) message. The text messagemay be predetermined, generated dynamically when the call is initiated,or any appropriate combination thereof. For example, the text messagemay comprise a predetermined message such as, for example, “Help,” “NeedAssistance,” etc. The predetermined text message may include the name ofthe person sending the message. The name of the person may be obtained,for example, from profile information stored on a mobile device 44, themobile device 44 may be programmed to store a subscriber's name, forincorporation into the text message, or any appropriate combinationthereof. Accordingly, the predetermined message may comprise a messagesuch as, for example, “Help, my name is Joe Smith,” “Need Assistance, myname is Joe Smith” etc.

The text message may comprise information that is determined dynamicallyas triggered by initiation of the call. For example, the text messagemay comprise location information, time, etc. In an example embodiment,the text message may comprise a current location of the mobile device44, the most recent known location of the mobile device 44, or the like,or any appropriate combination thereof. The text message may comprise atime at which the text message is being generated. Location informationmay be formatted in any appropriate manner, such as, for example,latitude, longitude, map coordinates, addresses, etc. In an exampleembodiment, location information may be formatted in accordance withgeographic code references such as the Federal Information ProcessingStandard (FIPS), ZIP codes, and/or the National Weather Service SpecificArea Message Encoder (SAME) codes, Geographic Information System (GIS)Alert Mapping Service, or the like, or any appropriate combinationthereof.

In an example embodiment, when the call is initiated, a prompt may berendered on the mobile device 44. The prompt may be provided in anyappropriate manner, such as, for example, visually, audibly,mechanically (e.g., vibration), or the like, or any appropriatecombination thereof. The prompt may indicate that a user 42 of themobile device 44 should speak, for example, into the device. The promptmay indicate that the user 42 should speak his/her name, location,and/or nature of the emergency. For example, upon determining, by themobile device 44, that the call is an emergency call, a message may bedisplayed on the mobile device 44 indicating that the user 42 should sayhis/her name, location, and nature of the emergency. The audioinformation spoken by the user 42 may be converted into text. Theconverted text may be incorporated into the text message.

The text message and/or signaling to establish a voice call session maybe provided to the mobile telephone switching office (MTSO) 48 via theradio access network (RAN) 46, at steps 62 and 64. As described in moredetail herein, the MTSO 48 may comprise systems, such as a MobileSwitching Center (MSC), for routing phone calls, connectivity to localand long distance networks, billing, and the like. The MTSO 48 may markthe text messaging session and the voice call session as havingcommonality. The MTSO 48 may mark or tag the text messaging session andthe voice call session in any appropriate manner. For example,information in each of the text messaging session and the voice callsession may be formatted to include an indication of the mobile device44 (e.g., international mobile subscriber identity, IMSI, a mobilesubscriber integrated services digital network number, MSISDN, etc.), anindication of a subscriber 42 associated with the mobile device 44, anidentification number indicated that the text messaging session and thevoice call session are correlated or paired, or the like, or anyappropriate combination thereof.

In an example embodiment, the MTSO 48 may determine if conditions aresufficient to establish and/or maintain a voice call. Conditions, orfactors, to be considered may include signal strength, battery power ofthe mobile device, propagation characteristics, obstructions, or thelike, or any appropriate combination thereof. In an example embodiment,signal strength (e.g., power, voltage, current, etc.) of a signalreceived by the mobile device may be analyzed. If it is determined thatthe received signal strength is less than a threshold value, it may bedetermined that conditions are not sufficient to establish and/ormaintain a voice call session. If it is determined that the receivedsignal strength is equal to or greater than a threshold value, it may bedetermined that conditions are sufficient to establish and/or maintain avoice call session. The threshold value may comprise any appropriatevalue, such as, for example, a value of power, a value of voltage, avalue of current, a percentage value of power, a percentage value ofvoltage, a percentage value of current, or the like, or any appropriatecombination thereof.

If the MTSO 48 determines that conditions are not sufficient toestablish and/or maintain a voice call session, the MTSO 48 maydetermine if conditions are sufficient for text messaging. Conditions,or factors, to be considered may include signal strength, battery powerof the mobile device, propagation characteristics, obstructions, or thelike, or any appropriate combination thereof. In an example embodiment,signal strength (e.g., power, voltage, current, etc.) of a signalreceived by the mobile device may be analyzed. If it is determined thatthe received signal strength is less than a threshold value, it may bedetermined that conditions are not sufficient to establish and/ormaintain a text call session. If it is determined that the receivedsignal strength is equal to or greater than a threshold value, it may bedetermined that conditions are sufficient to establish and/or maintain atext call session. The threshold value may comprise any appropriatevalue, such as, for example, a value of power, a value of voltage, avalue of current, a percentage value of power, a percentage value ofvoltage, a percentage value of current, or the like, or any appropriatecombination thereof.

If the MTSO 48 determines that conditions are not sufficient toestablish and/or maintain a text messaging session and the conditionsare not sufficient to establish and/or maintain a voice session, theMTSO 48 try again. If the MTSO 48 determines that conditions aresufficient to establish and/or maintain a voice call session, the voicecall may be forwarded to the voice network 52 and step 66. Optionally,if the MTSO 48 determines that conditions are sufficient to establishand/or maintain a voice call session, the voice call and the textmessage may be forwarded. The voice call may be forwarded to the voicenetwork 52 and step 66 and the text message may be forwarded to the datanetwork 50 at step 68. The voice network 52 and the data network 50 maycomprise any appropriate network. For example, the voice network 52 maycomprise any appropriate network capable of communicating voice. Thedata network 50 may comprise any appropriate network capable ofcommunicating data, text, or any appropriate combination thereof. In anexample embodiment, the data network 50 may comprise text a networkcapable of communications via the short messaging service (SMS) system.

In an example embodiment, a voice call may originate in the WirelessNetwork. The voice call may traverse the wireless network to an egresspoint (e.g., Long Distance TDM network, Local TDM Network with LegacySelective router, directly terminate on the Emergency Services IPnetwork, etc.). The Short Message Service (SMS) is a text messagingservice component of phone, web, or mobile communication system that mayuse communications protocols that may allow the exchange of textmessages between fixed line and/or mobile devices. Mobile-to-mobile SMStext messages may be delivered using the Short Message Peer-to-Peer(SMPP) protocol over an IP network. SMS may be available on networkssuch as, for example, GSM, 3G, 4G, etc. Not all text messagesnecessarily need to use the SMS. A text message may egress through theShort Message Service Center (SMSC) platform in the wireless network,through a Text Gateway Server, to the Emergency Services IP network. Thegateway server may perform the conversion from SMPP to SIP.

If the MTSO 48 determines that conditions are sufficient to establishand/or maintain a voice call session, the voice call may be forwarded tothe voice network 52 at step 66. Optionally, if the MTSO 48 determinesthat conditions are sufficient to establish and/or maintain a voice callsession, the voice call and the text message may be forwarded at steps66 and 68. The voice call may be forwarded via voice network 52 and thetext message may be forwarded via data network 50. As described above,the MTSO may mark the voice call and the corresponding text (e.g., SMS)message as having commonality, originating from the same source, etc.and forward them to the appropriate destination via separate paths.Thus, when the two communications (e.g., voice and text) are received,the PSAP 58 for example, equipment at the PSAP 58 may be able todetermine that the two communications are correlated (have commonality)and process them accordingly. This may be based on a Pseudo-ANI andCalling Party Number. The MTSO may generate the Pseudo-ANI, which isassociated with the cell tower serving the calling party, to determinethe appropriate Service Provider to which the voice call may beforwarded. The Calling Party Number may identify the device. As the textmessage is forwarded to an SMS gateway, the Emergency Call RoutingFunction (ECRF) may be accessed to perform a LoST (Location to ServiceTranslation) function to determine an appropriate ESI-Net based on thecalling party's location information. The intelligence in the EmergencyServices IP Network Selective Router (providing call routing and callcontrol) may correlate the voice and text components and deliver theappropriate information to the 9-1-1 agent at the PSAP. The protocolused in the ESI-Net would be SIP.

The voice path may comprise trunking to the voice network 52, which maycomprise, for example, a local and/or long distance voice network. In anexample embodiment, signaling associated with the voice call may becarried over the data network 50, which may comprise, for example, a SS7data network, or the like. In an example embodiment, the voice call maybe established using SS7 signaling and the Pseudo-ANI and Calling PartyNumber and other parameters may be available to identify the caller.These parameters may be interworked into the SIP protocol by a TDM/IPgateway of the ESI-Net.

The text message (e.g., SMS text message) also may utilize the datanetwork 50 (e.g., telephony SS7 signaling network) for transport and maybe interleaved with voice signaling traffic. In an example embodiment,voice calls may be forwarded to the emergency services IP network 56 viaa tandem office 54 at steps 68 and 70. The tandem office 54 may compriseany appropriate entity capable of providing communications between thevoice network 52 and the emergency services IP network 56. An E 9-1-1legacy selective router may comprise software that resides on a tandemswitching element within a legacy TDM network that may receive 9-1-1calls originated with the Public Telephone Network, may route the callto the appropriate PSAP, and may provide the signaling interface to thePSAP itself. If there is not a direct voice link from the MTSO to thePSAP, the legacy selective router tandem may provide the switching toestablish the path. Over time, the selective router function may beabsorbed into the IP based selective router in the ESI-Net. The legacytandem selective router and the ESI-Net selective router may co-exist inthe network.

If the MTSO 48 determines that conditions are sufficient to establishand/or maintain a text messaging session, but not sufficient toestablish and/or maintain a voice session, the text message may beforwarded to the data network 50 at step 68. The text message may beforwarded to the emergency services IP network 56 from the MTSO 48, viathe data network 50, at steps 68 and 76.

The emergency services IP network 56 may comprise, for example, anyappropriate entity capable of receiving voice and text communicationsand communicating (step 72) with a PSAP 58. In an example embodiment,the emergency services IP network 56 may comprise circuitry thatprovides communication between the data network 50 and the PSAP 58. Theemergency services IP network 56 also may comprise circuitry thatprovides communication between the voice network 52 (optionally via thetandem office 54) and the PSAP 58. In an example embodiment, theemergency services IP network 56 may comprise a time divisionmultiplexing (TDM) to IP gateway that provides communication between thesignaling system number 7 (SS7) and the session initiation protocol(SIP) for signaling and real-time transport (RTP) for packetized voice,a selective router for routing the voice and text information to theappropriate Public Safety Answering Point (PSAP) 58, and a sessionborder controller (SBC) to exert control over signaling and media pathsand security between the service provider network and the governmentnetwork supporting the PSAP infrastructure 58. In an example embodiment,a TDM/IP Gateway comprises a gateway between a legacy TDM network and aNext-Generation 9-1-1 Emergency Services IP Network that interworkslegacy TDM signaling such as SS7 ISUP or MF CAMA (Centralized AutomaticMessage Accounting) with SIP (Session Initiation Protocol) signaling. Inan example embodiment, a Next-Generation ESInet Selective Routingcomprises a function in the Next Gen ESInet that may selectively route9-1-1 calls to PSAPs. In addition to wireline and wireless calls, theESInet selective routing function may also receive and process nativeVoIP calls as well as text, video, picture and future technologies. Inan example embodiment, a Session Border Controller (SBC) may comprise afunctional element that may provide security, NAT (Network AddressTranslation) traversal, protocol repair, and other functions to VoIPsignaling such as SIP, for example. SBC may be a component of a BorderControl Function.

In an example embodiment, the selective router of the emergency servicesIP network 56 may correlate the voice call and the text message thathave commonality and forward both (the voice call and the text message)to the same agent 60 in the PSAP 58. The selective router may continueto coordinate with an automatic call distribution (ACD) function of thePSAP 58 to assure that subsequent text messages are delivered to thesame agent 60 for continuity.

If the communication received by equipment of the PSAP 58 is a textmessage only, communication may be established/maintained betweenequipment of the PSAP 58 and the mobile device 44 via text at step 74.If the communication received by equipment of the PSAP 58 is a voiceonly, communication may be established/maintained between equipment ofthe PSAP 58 and the mobile device 44 via voice at step 74. If thecommunication received by equipment of the PSAP 58 is a voice and text,communication may be established/maintained between equipment of thePSAP 58 and the mobile device 44 via voice at step 74 and optionally viatext.

In an example embodiment, if the voice call between equipment at thePSAP 58 and the mobile device 44 is dropped, lost, or becomesintermittent, the communication may be switched over to a textcommunication. For example, after trying to establish a voice call, thePSAP may launch a text message in an attempt to reconnect with themobile device. The PSAP may communicate its request to the ESI-NetSelective Router, which may retain incoming text messages for aspecified period of time. After retrieving the associated record, theESI-Net selective router may attempt to re-establish the connectionthrough the originating SMS Gateway.

FIG. 3 is a block diagram of an example communications device 80configured to facilitate text message generation for emergency servicesas a backup to voice communications. In an example embodiment, thecommunications device 80 may comprise the mobile device 44. In anexample configuration, communications device 80 comprises a mobilewireless device. The communications device 80, however, may comprise anyappropriate device, examples of which include a portable computingdevice, such as a laptop, a personal digital assistant (“PDA”), aportable phone (e.g., a cell phone or the like, a smart phone, a videophone), a portable email device, a portable gaming device, a TV, a DVDplayer, portable media player, (e.g., a portable music player, such asan MP3 player, a Walkman, etc.), a portable navigation device (e.g., GPScompatible device, A-GPS compatible device, etc.), or a combinationthereof. The communications device 80 can include devices that are nottypically thought of as portable, such as, for example, a publiccomputing device, a navigation device installed in-vehicle, a set topbox, or the like. The mobile communications device 80 can includenon-conventional computing devices, such as, for example, a kitchenappliance, a motor vehicle control (e.g., steering wheel), etc., or thelike. As evident from the herein description a communications device, amobile device, or any portion thereof is not to be construed as softwareper se.

The communications device 80 may include any appropriate device,mechanism, software, and/or hardware for facilitating text messagegeneration for emergency services as a backup to voice communications asdescribed herein. In an example embodiment, the ability to facilitatetext message generation for emergency services as a backup to voicecommunications is a feature of the communications device 80 that can beturned on and off Thus, in an example embodiment, an owner of thecommunications device 80 may opt-in or opt-out of this capability.

In an example embodiment, the communications device 80 comprises aprocessor and memory coupled to the processor. The memory may compriseexecutable instructions that when executed by the processor cause theprocessor to effectuate operations associated with text messagegeneration for emergency services as a backup to voice communications.

In an example configuration, the communications device 80 comprises aprocessing portion 82, a memory portion 84, an input/output portion 86,and a user interface (UI) portion 88. Each portion of the communicationsdevice 80 comprises circuitry for performing functions associated witheach respective portion. Thus, each portion can comprise hardware, or acombination of hardware and software. Accordingly, each portion of thecommunications device 80 is not to be construed as software per se. Itis emphasized that the block diagram depiction of communications device80 is exemplary and not intended to imply a specific implementationand/or configuration. For example, in an example configuration, thecommunications device 80 may comprise a cellular phone and theprocessing portion 82 and/or the memory portion 84 may be implemented,in part or in total, on a subscriber identity module (SIM) of the mobilecommunications device 80. In another example configuration, thecommunications device 80 may comprise a laptop computer. The laptopcomputer can include a SIM, and various portions of the processingportion 82 and/or the memory portion 84 can be implemented on the SIM,on the laptop other than the SIM, or any combination thereof.

The processing portion 82, memory portion 84, and input/output portion86 are coupled together to allow communications therebetween. In variousembodiments, the input/output portion 86 comprises a receiver of thecommunications device 80, a transmitter of the communications device 80,or a combination thereof. The input/output portion 86 is capable ofreceiving and/or providing information pertaining to text messagegeneration for emergency services as a backup to voice communications asdescribed herein. In various configurations, the input/output portion 86may receive and/or provide information via any appropriate means, suchas, for example, optical means (e.g., infrared), electromagnetic means(e.g., RF, WI-FI, BLUETOOTH, ZIGBEE, etc.), acoustic means (e.g.,speaker, microphone, ultrasonic receiver, ultrasonic transmitter), or acombination thereof.

The processing portion 82 may be capable of performing functionspertaining to text message generation for emergency services as a backupto voice communications as described herein. In a basic configuration,the communications device 80 may include at least one memory portion 84.The memory portion 84 may comprise a storage medium having a tangiblephysical structure. Thus, the memory portion 84, as well as anycomputer-readable storage medium described herein, is not to beconstrued as a transient signal per se. Further, the memory portion 84,as well as any computer-readable storage medium described herein, is notto be construed as a propagating signal per se. The memory portion 84may store any information utilized in conjunction with the text messagegeneration for emergency services as a backup to voice communications asdescribed herein. Depending upon the exact configuration and type ofprocessor, the memory portion 84 may be volatile (such as some types ofRAM), non-volatile (such as ROM, flash memory, etc.), or a combinationthereof. The mobile communications device 80 may include additionalstorage (e.g., removable storage and/or non-removable storage)including, but not limited to, tape, flash memory, smart cards, CD-ROM,digital versatile disks (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, universal serial bus (USB) compatible memory, or anyother medium which can be used to store information and which can beaccessed by the mobile communications device 80.

The communications device 80 also may contain a user interface (UI)portion 88 allowing a user to communicate with the communications device80. The UI portion 88 may be capable of rendering any informationutilized in conjunction with text message generation for emergencyservices as a backup to voice communications as described herein. The UIportion 88 may provide the ability to control the communications device80, via, for example, buttons, soft keys, voice actuated controls, atouch screen, movement of the mobile communications device 80, visualcues (e.g., moving a hand in front of a camera on the mobilecommunications device 80), or the like. The UI portion 88 may providevisual information (e.g., via a display), audio information (e.g., viaspeaker), mechanically (e.g., via a vibrating mechanism), or acombination thereof. In various configurations, the UI portion 88 maycomprise a display, a touch screen, a keyboard, an accelerometer, amotion detector, a speaker, a microphone, a camera, a tilt sensor, orany combination thereof. The UI portion 88 may comprise means forinputting biometric information, such as, for example, fingerprintinformation, retinal information, voice information, and/or facialcharacteristic information.

The UI portion 88 may include a display for displaying multimedia suchas, for example, application graphical user interfaces (GUIs), text,images, video, telephony functions such as Caller ID data, setupfunctions, menus, music, metadata, messages, wallpaper, graphics,Internet content, device status, preferences settings, map and locationdata, routes and other directions, points of interest (POI), and thelike.

In some embodiments, the UI portion may comprise a user interface (UI)application. The UI application may interface with a client or operatingsystem (OS) to, for example, facilitate user interaction with devicefunctionality and data. The UI application may aid a user in enteringmessage content, viewing received messages, answering/initiating calls,entering/deleting data, entering and setting user IDs and passwords,configuring settings, manipulating content and/or settings, interactingwith other applications, or the like, and may aid the user in inputtingselections associated with text message generation for emergencyservices as a backup to voice communications as described herein.

FIG. 4 is a block diagram of an example network entity 90 for textmessage generation for emergency services as a backup to voicecommunications. The network entity 90 may comprise hardware or acombination of hardware and software. When used in conjunction with anetwork, the functionality needed to facilitate text message generationfor emergency services as a backup to voice communications can reside inany one or combination of network entities. The network entity 90depicted in FIG. 4 represents any appropriate network entity, orcombination of network entities, such as a processor, a server, agateway, a node, any appropriate entity depicted in FIG. 5, anyappropriate entity depicted in FIG. 6, any appropriate entity depictedin FIG. 7, any appropriate entity depicted in FIG. 8, the MTSO depictedin FIG. 2, any appropriate entity, component, device, and/or circuitryof the MTSO depicted in FIG. 2, any appropriate entity, component,device, and/or circuitry of the voice network depicted in FIG. 2, anyappropriate entity, component, device, and/or circuitry of the datanetwork depicted in FIG. 2, any appropriate entity, component, device,and/or circuitry of the tandem office depicted in FIG. 2, anyappropriate entity, component, device, and/or circuitry of the emergencyservices IP network depicted in FIG. 2, any appropriate entity,component, device, and/or circuitry of the PSAP depicted in FIG. 2, orany appropriate combination thereof. In an example configuration, thenetwork entity 90 comprises a component or various components of acellular broadcast system wireless network. It is emphasized that theblock diagram depicted in FIG. 4 is exemplary and not intended to implya specific implementation or configuration. Thus, the network entity 90can be implemented in a single processor or multiple processors (e.g.,single server or multiple servers, single gateway or multiple gateways,etc.). Multiple network entities can be distributed or centrallylocated. Multiple network entities can communicate wirelessly, via hardwire, or a combination thereof.

In an example embodiment, the network entity 90 comprises a processorand memory coupled to the processor. The memory may comprise executableinstructions that when executed by the processor cause the processor toeffectuate operations associated with text message generation foremergency services as a backup to voice communications. As evident fromthe herein description a network entity or any portion thereof is not tobe construed as software per se.

In an example embodiment, the network entity 90 comprises a processorand memory coupled to the processor. The memory may comprise executableinstructions that when executed by the processor cause the processor toeffectuate operations associated with text message generation foremergency services as a backup to voice communications.

In an example configuration, the network entity 90 comprises aprocessing portion 92, a memory portion 94, and an input/output portion96. The processing portion 92, memory portion 94, and input/outputportion 96 are coupled together (coupling not shown in FIG. 4) to allowcommunications therebetween. The input/output portion 96 may be capableof receiving and/or providing information from/to a communicationsdevice and/or other network entities configured to be utilized with textmessage generation for emergency services as a backup to voicecommunications. For example, the input/output portion 96 may include awireless communications (e.g., 2.5G/3G/4G/GPS) card. The input/outputportion 96 may be capable of receiving and/or sending video information,audio information, control information, image information, data, or anycombination thereof. In an example embodiment, the input/output portion36 may be capable of receiving and/or sending information to determine alocation of the network entity 90 and/or the communications device 30.In an example configuration, the input\output portion 96 may comprise aGPS receiver. In an example configuration, the network entity 90 maydetermine its own geographical location and/or the geographical locationof a communications device through any type of location determinationsystem including, for example, the Global Positioning System (GPS),assisted GPS (A-GPS), time difference of arrival calculations,configured constant location (in the case of non-moving devices), anycombination thereof, or any other appropriate means. In variousconfigurations, the input/output portion 96 may receive and/or provideinformation via any appropriate means, such as, for example, opticalmeans (e.g., infrared), electromagnetic means (e.g., RF, WI-FI,BLUETOOTH, ZIGBEE, etc.), acoustic means (e.g., speaker, microphone,ultrasonic receiver, ultrasonic transmitter), or a combination thereof.In an example configuration, the input/output portion may comprise aWIFI finder, a two way GPS chipset or equivalent, or the like, or acombination thereof.

The processing portion 92 may be capable of performing functionsassociated with text message generation for emergency services as abackup to voice communications as described herein. That is, acommunications device can perform functions internally (by the device)and/or utilize the network entity 90 to perform functions. For example,the processing portion 92 may be capable of, in conjunction with anyother portion of the network entity 90, installing an application fortext message generation for emergency services as a backup to voicecommunications, processing an application for text message generationfor emergency services as a backup to voice communications, configuringthe network entity 90 to function as a gateway for other devices to anetwork, determining the location at which to provide text messagegeneration for emergency services as a backup to voice communications,determining the duration during which to provide text message generationfor emergency services as a backup to voice communications, or the like,or any combination thereof. The processing portion 92, in conjunctionwith any other portion of the network entity 90, enables the networkentity 90 to covert speech to text when it is configured to also sendtext messages while utilizing the event based service.

In a basic configuration, the network entity 90 may include at least onememory portion 94. The memory portion 94 may comprise a storage mediumhaving a tangible physical structure. Thus, the memory portion 94, aswell as any computer-readable storage medium described herein, is not tobe construed as a transient signal per se. The memory portion 94, aswell as any computer-readable storage medium described herein, is not tobe construed as a propagating signal per se. The memory portion 94 maystore any information utilized in conjunction with text messagegeneration for emergency services as a backup to voice communications asdescribed herein. Depending upon the exact configuration and type ofprocessor, the memory portion 94 may be volatile 98 (such as some typesof RAM), non-volatile 100 (such as ROM, flash memory, etc.), or acombination thereof. The network entity 90 may include additionalstorage (e.g., removable storage 102 and/or non-removable storage 104)including, but not limited to, tape, flash memory, smart cards, CD-ROM,digital versatile disks (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, universal serial bus (USB) compatible memory, or anyother medium which can be used to store information and which can beaccessed by the network entity 90.

The network entity 90 also may contain communications connection(s) 110that allow the network entity 90 to communicate with other devices,network entities, or the like. A communications connection(s) cancomprise communication media. Communication media typically embodycomputer readable instructions, data structures, program modules orother data in a modulated data signal such as a carrier wave or othertransport mechanism and includes any information delivery media. By wayof example, and not limitation, communication media include wired mediasuch as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared, and other wireless media. The termcomputer readable media as used herein includes both storage media andcommunication media. The network entity 90 also can include inputdevice(s) 106 such as keyboard, mouse, pen, voice input device, touchinput device, etc. Output device(s) 108 such as a display, speakers,printer, etc. also can be included.

A communications device and/or network entity may be part of and/or incommunications with various wireless communications networks. Some ofwhich are described below.

FIG. 5 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network, withinwhich text message generation for emergency services as a backup tovoice communications may be implemented. In the example packet-basedmobile cellular network environment shown in FIG. 5, there are aplurality of Base Station Subsystems (“BSS”) 800 (only one is shown),each of which comprises a Base Station Controller (“BSC”) 802 serving aplurality of Base Transceiver Stations (“BTS”) such as BTSs 804, 806,and 808. BTSs 804, 806, 808, etc. are the access points where users ofpacket-based mobile devices become connected to the wireless network. Inexample fashion, the packet traffic originating from user devices istransported via an over-the-air interface to a BTS 808, and from the BTS808 to the BSC 802. Base station subsystems, such as BSS 800, are a partof internal frame relay network 810 that can include Service GPRSSupport Nodes (“SGSN”) such as SGSN 812 and 814. Each SGSN is connectedto an internal packet network 820 through which a SGSN 812, 814, etc.can route data packets to and from a plurality of gateway GPRS supportnodes (GGSN) 822, 824, 826, etc. As illustrated, SGSN 814 and GGSNs 822,824, and 826 are part of internal packet network 820. Gateway GPRSserving nodes 822, 824 and 826 mainly provide an interface to externalInternet Protocol (“IP”) networks such as Public Land Mobile Network(“PLMN”) 850, corporate intranets 840, or Fixed-End System (“FES”) orthe public Internet 830. As illustrated, subscriber corporate network840 may be connected to GGSN 824 via firewall 832; and PLMN 850 isconnected to GGSN 824 via boarder gateway router 834. The RemoteAuthentication Dial-In User Service (“RADIUS”) server 842 may be usedfor caller authentication when a user of a mobile cellular device callscorporate network 840.

Generally, there can be a several cell sizes in a GSM network, referredto as macro, micro, pico, femto and umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro-cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential, or smallbusiness environments. On the other hand, umbrella cells are used tocover shadowed regions of smaller cells and fill in gaps in coveragebetween those cells.

FIG. 6 illustrates an architecture of a typical GPRS network withinwhich text message generation for emergency services as a backup tovoice communications can be implemented. The architecture depicted inFIG. 6 is segmented into four groups: users 950, radio access network960, core network 970, and interconnect network 980. Users 950 comprisea plurality of end users. Note, device 912 is referred to as a mobilesubscriber in the description of network shown in FIG. 6. In an exampleembodiment, the device depicted as mobile subscriber 912 comprises acommunications device (e.g., communications device 160). Radio accessnetwork 960 comprises a plurality of base station subsystems such asBSSs 962, which include BTSs 964 and BSCs 966. Core network 970comprises a host of various network elements. As illustrated in FIG. 6,core network 970 may comprise Mobile Switching Center (“MSC”) 971,Service Control Point (“SCP”) 972, gateway MSC 973, SGSN 976, HomeLocation Register (“HLR”) 974, Authentication Center (“AuC”) 975, DomainName Server (“DNS”) 977, and GGSN 978. Interconnect network 980 alsocomprises a host of various networks and other network elements. Asillustrated in FIG. 6, interconnect network 980 comprises PublicSwitched Telephone Network (“PSTN”) 982, Fixed-End System (“FES”) orInternet 984, firewall 988, and Corporate Network 989.

A mobile switching center can be connected to a large number of basestation controllers. At MSC 971, for instance, depending on the type oftraffic, the traffic may be separated in that voice may be sent toPublic Switched Telephone Network (“PSTN”) 982 through Gateway MSC(“GMSC”) 973, and/or data may be sent to SGSN 976, which then sends thedata traffic to GGSN 978 for further forwarding.

When MSC 971 receives call traffic, for example, from BSC 966, it sendsa query to a database hosted by SCP 972. The SCP 972 processes therequest and issues a response to MSC 971 so that it may continue callprocessing as appropriate.

The HLR 974 is a centralized database for users to register to the GPRSnetwork. HLR 974 stores static information about the subscribers such asthe International Mobile Subscriber Identity (“IMSI”), subscribedservices, and a key for authenticating the subscriber. HLR 974 alsostores dynamic subscriber information such as the current location ofthe mobile subscriber. Associated with HLR 974 is AuC 975. AuC 975 is adatabase that contains the algorithms for authenticating subscribers andincludes the associated keys for encryption to safeguard the user inputfor authentication.

In the following, depending on context, the term “mobile subscriber”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 6, whenmobile subscriber 912 initiates the attach process by turning on thenetwork capabilities of the mobile device, an attach request is sent bymobile subscriber 912 to SGSN 976. The SGSN 976 queries another SGSN, towhich mobile subscriber 912 was attached before, for the identity ofmobile subscriber 912. Upon receiving the identity of mobile subscriber912 from the other SGSN, SGSN 976 requests more information from mobilesubscriber 912. This information is used to authenticate mobilesubscriber 912 to SGSN 976 by HLR 974. Once verified, SGSN 976 sends alocation update to HLR 974 indicating the change of location to a newSGSN, in this case SGSN 976. HLR 974 notifies the old SGSN, to whichmobile subscriber 912 was attached before, to cancel the locationprocess for mobile subscriber 912. HLR 974 then notifies SGSN 976 thatthe location update has been performed. At this time, SGSN 976 sends anAttach Accept message to mobile subscriber 912, which in turn sends anAttach Complete message to SGSN 976.

After attaching itself with the network, mobile subscriber 912 then goesthrough the authentication process. In the authentication process, SGSN976 sends the authentication information to HLR 974, which sendsinformation back to SGSN 976 based on the user profile that was part ofthe user's initial setup. The SGSN 976 then sends a request forauthentication and ciphering to mobile subscriber 912. The mobilesubscriber 912 uses an algorithm to send the user identification (ID)and password to SGSN 976. The SGSN 976 uses the same algorithm andcompares the result. If a match occurs, SGSN 976 authenticates mobilesubscriber 912.

Next, the mobile subscriber 912 establishes a user session with thedestination network, corporate network 989, by going through a PacketData Protocol (“PDP”) activation process. Briefly, in the process,mobile subscriber 912 requests access to the Access Point Name (“APN”),for example, UPS.com, and SGSN 976 receives the activation request frommobile subscriber 912. SGSN 976 then initiates a Domain Name Service(“DNS”) query to learn which GGSN node has access to the UPS.com APN.The DNS query is sent to the DNS server within the core network 970,such as DNS 977, which is provisioned to map to one or more GGSN nodesin the core network 970. Based on the APN, the mapped GGSN 978 canaccess the requested corporate network 989. The SGSN 976 then sends toGGSN 978 a Create Packet Data Protocol (“PDP”) Context Request messagethat contains necessary information. The GGSN 978 sends a Create PDPContext Response message to SGSN 976, which then sends an Activate PDPContext Accept message to mobile subscriber 912.

Once activated, data packets of the call made by mobile subscriber 912can then go through radio access network 960, core network 970, andinterconnect network 980, in a particular fixed-end system or Internet984 and firewall 988, to reach corporate network 989.

FIG. 7 illustrates an example block diagram view of a GSM/GPRS/IPmultimedia network architecture within which text message generation foremergency services as a backup to voice communications may beimplemented. As illustrated, the architecture of FIG. 7 includes a GSMcore network 1001, a GPRS network 1030 and an IP multimedia network1038. The GSM core network 1001 includes a Mobile Station (MS) 1002, atleast one Base Transceiver Station (BTS) 1004 and a Base StationController (BSC) 1006. The MS 1002 is physical equipment or MobileEquipment (ME), such as a mobile phone or a laptop computer that is usedby mobile subscribers, with a Subscriber identity Module (SIM) or aUniversal Integrated Circuit Card (UICC). The SIM or UICC includes anInternational Mobile Subscriber Identity (IMSI), which is a uniqueidentifier of a subscriber. The BTS 1004 is physical equipment, such asa radio tower, that enables a radio interface to communicate with theMS. Each BTS may serve more than one MS. The BSC 1006 manages radioresources, including the BTS. The BSC may be connected to several BTSs.The BSC and BTS components, in combination, are generally referred to asa base station (BSS) or radio access network (RAN) 1003.

The GSM core network 1001 also includes a Mobile Switching Center (MSC)1008, a Gateway Mobile Switching Center (GMSC) 1010, a Home LocationRegister (HLR) 1012, Visitor Location Register (VLR) 1014, anAuthentication Center (AuC) 1018, and an Equipment Identity Register(EIR) 1016. The MSC 1008 performs a switching function for the network.The MSC also performs other functions, such as registration,authentication, location updating, handovers, and call routing. The GMSC1010 provides a gateway between the GSM network and other networks, suchas an Integrated Services Digital Network (ISDN) or Public SwitchedTelephone Networks (PSTNs) 1020. Thus, the GMSC 1010 providesinterworking functionality with external networks.

The HLR 1012 is a database that contains administrative informationregarding each subscriber registered in a corresponding GSM network. TheHLR 1012 also contains the current location of each MS. The VLR 1014 isa database that contains selected administrative information from theHLR 1012. The VLR contains information necessary for call control andprovision of subscribed services for each MS currently located in ageographical area controlled by the VLR. The HLR 1012 and the VLR 1014,together with the MSC 1008, provide the call routing and roamingcapabilities of GSM. The AuC 1016 provides the parameters needed forauthentication and encryption functions. Such parameters allowverification of a subscriber's identity. The EIR 1018 storessecurity-sensitive information about the mobile equipment.

A Short Message Service Center (SMSC) 1009 allows one-to-one ShortMessage Service (SMS) messages to be sent to/from the MS 1002. A PushProxy Gateway (PPG) 1011 is used to “push” (i.e., send without asynchronous request) content to the MS 1002. The PPG 1011 acts as aproxy between wired and wireless networks to facilitate pushing of datato the MS 1002. A Short Message Peer to Peer (SMPP) protocol router 1013is provided to convert SMS-based SMPP messages to cell broadcastmessages. SMPP is a protocol for exchanging SMS messages between SMSpeer entities such as short message service centers. The SMPP protocolis often used to allow third parties, e.g., content suppliers such asnews organizations, to submit bulk messages.

To gain access to GSM services, such as speech, data, and short messageservice (SMS), the MS first registers with the network to indicate itscurrent location by performing a location update and IMSI attachprocedure. The MS 1002 sends a location update including its currentlocation information to the MSC/VLR, via the BTS 1004 and the BSC 1006.The location information is then sent to the MS's HLR. The HLR isupdated with the location information received from the MSC/VLR. Thelocation update also is performed when the MS moves to a new locationarea. Typically, the location update is periodically performed to updatethe database as location updating events occur.

The GPRS network 1030 is logically implemented on the GSM core networkarchitecture by introducing two packet-switching network nodes, aserving GPRS support node (SGSN) 1032, a cell broadcast and a GatewayGPRS support node (GGSN) 1034. The SGSN 1032 is at the same hierarchicallevel as the MSC 1008 in the GSM network. The SGSN controls theconnection between the GPRS network and the MS 1002. The SGSN also keepstrack of individual MS's locations and security functions and accesscontrols.

A Cell Broadcast Center (CBC) 1014 communicates cell broadcast messagesthat are typically delivered to multiple users in a specified area. CellBroadcast is one-to-many geographically focused service. It enablesmessages to be communicated to multiple mobile phone customers who arelocated within a given part of its network coverage area at the time themessage is broadcast.

The GGSN 1034 provides a gateway between the GPRS network and a publicpacket network (PDN) or other IP networks 1036. That is, the GGSNprovides interworking functionality with external networks, and sets upa logical link to the MS through the SGSN. When packet-switched dataleaves the GPRS network, it is transferred to an external TCP-IP network1036, such as an X.25 network or the Internet. In order to access GPRSservices, the MS first attaches itself to the GPRS network by performingan attach procedure. The MS then activates a packet data protocol (PDP)context, thus activating a packet communication session between the MS,the SGSN, and the GGSN.

In a GSM/GPRS network, GPRS services and GSM services can be used inparallel. The MS can operate in one of three classes: class A, class B,and class C. A class A MS can attach to the network for both GPRSservices and GSM services simultaneously. A class A MS also supportssimultaneous operation of GPRS services and GSM services. For example,class A mobiles can receive GSM voice/data/SMS calls and GPRS data callsat the same time.

A class B MS can attach to the network for both GPRS services and GSMservices simultaneously. However, a class B MS does not supportsimultaneous operation of the GPRS services and GSM services. That is, aclass B MS can only use one of the two services at a given time.

A class C MS can attach for only one of the GPRS services and GSMservices at a time. Simultaneous attachment and operation of GPRSservices and GSM services is not possible with a class C MS.

A GPRS network 1030 can be designed to operate in three networkoperation modes (NOM1, NOM2 and NOM3). A network operation mode of aGPRS network is indicated by a parameter in system information messagestransmitted within a cell. The system information messages dictates a MSwhere to listen for paging messages and how to signal towards thenetwork. The network operation mode represents the capabilities of theGPRS network. In a NOM1 network, a MS can receive pages from a circuitswitched domain (voice call) when engaged in a data call. The MS cansuspend the data call or take both simultaneously, depending on theability of the MS. In a NOM2 network, a MS may not receive pages from acircuit switched domain when engaged in a data call, since the MS isreceiving data and is not listening to a paging channel. In a NOM3network, a MS can monitor pages for a circuit switched network whilereceived data and vice versa.

The IP multimedia network 1038 was introduced with 3GPP Release 5, andincludes an IP multimedia subsystem (IMS) 1040 to provide richmultimedia services to end users. A representative set of the networkentities within the IMS 1040 are a call/session control function (CSCF),a media gateway control function (MGCF) 1046, a media gateway (MGW)1048, and a master subscriber database, called a home subscriber server(HSS) 1050. The HSS 1050 may be common to the GSM network 1001, the GPRSnetwork 1030 as well as the IP multimedia network 1038.

The IP multimedia system 1040 is built around the call/session controlfunction, of which there are three types: an interrogating CSCF (I-CSCF)1043, a proxy CSCF (P-CSCF) 1042, and a serving CSCF (S-CSCF) 1044. TheP-CSCF 1042 is the MS's first point of contact with the IMS 1040. TheP-CSCF 1042 forwards session initiation protocol (SIP) messages receivedfrom the MS to an SIP server in a home network (and vice versa) of theMS. The P-CSCF 1042 may also modify an outgoing request according to aset of rules defined by the network operator (for example, addressanalysis and potential modification).

The I-CSCF 1043, forms an entrance to a home network and hides the innertopology of the home network from other networks and providesflexibility for selecting an S-CSCF. The I-CSCF 1043 may contact asubscriber location function (SLF) 1045 to determine which HSS 1050 touse for the particular subscriber, if multiple HSS's 1050 are present.The S-CSCF 1044 performs the session control services for the MS 1002.This includes routing originating sessions to external networks androuting terminating sessions to visited networks. The S-CSCF 1044 alsodecides whether an application server (AS) 1052 is required to receiveinformation on an incoming SIP session request to ensure appropriateservice handling. This decision is based on information received fromthe HSS 1050 (or other sources, such as an application server 1052). TheAS 1052 also communicates to a location server 1056 (e.g., a GatewayMobile Location Center (GMLC)) that provides a position (e.g.,latitude/longitude coordinates) of the MS 1002.

The HSS 1050 contains a subscriber profile and keeps track of which corenetwork node is currently handling the subscriber. It also supportssubscriber authentication and authorization functions (AAA). In networkswith more than one HSS 1050, a subscriber location function providesinformation on the HSS 1050 that contains the profile of a givensubscriber.

The MGCF 1046 provides interworking functionality between SIP sessioncontrol signaling from the IMS 1040 and ISUP/BICC call control signalingfrom the external GSTN networks (not shown). It also controls the mediagateway (MGW) 1048 that provides user-plane interworking functionality(e.g., converting between AMR- and PCM-coded voice). The MGW 1048 alsocommunicates with other IP multimedia networks 1054.

Push to Talk over Cellular (PoC) capable mobile phones register with thewireless network when the phones are in a predefined area (e.g., jobsite, etc.). When the mobile phones leave the area, they register withthe network in their new location as being outside the predefined area.This registration, however, does not indicate the actual physicallocation of the mobile phones outside the pre-defined area.

FIG. 8 illustrates a PLMN block diagram view of an example architecturein which text message generation for emergency services as a backup tovoice communications may be incorporated. Mobile Station (MS) 1401 isthe physical equipment used by the PLMN subscriber. In one illustrativeembodiment, communications device 200 may serve as Mobile Station 1401.Mobile Station 1401 may be one of, but not limited to, a cellulartelephone, a cellular telephone in combination with another electronicdevice or any other wireless mobile communication device.

Mobile Station 1401 may communicate wirelessly with Base Station System(BSS) 1410. BSS 1410 contains a Base Station Controller (BSC) 1411 and aBase Transceiver Station (BTS) 1412. BSS 1410 may include a single BSC1411/BTS 1412 pair (Base Station) or a system of BSC/BTS pairs which arepart of a larger network. BSS 1410 is responsible for communicating withMobile Station 1401 and may support one or more cells. BSS 1410 isresponsible for handling cellular traffic and signaling between MobileStation 1401 and Core Network 1440. Typically, BSS 1410 performsfunctions that include, but are not limited to, digital conversion ofspeech channels, allocation of channels to mobile devices, paging, andtransmission/reception of cellular signals.

Additionally, Mobile Station 1401 may communicate wirelessly with RadioNetwork System (RNS) 1420. RNS 1420 contains a Radio Network Controller(RNC) 1421 and one or more Node(s) B 1422. RNS 1420 may support one ormore cells. RNS 1420 may also include one or more RNC 1421/Node B 1422pairs or alternatively a single RNC 1421 may manage multiple Nodes B1422. RNS 1420 is responsible for communicating with Mobile Station 1401in its geographically defined area. RNC 1421 is responsible forcontrolling the Node(s) B 1422 that are connected to it and is a controlelement in a UMTS radio access network. RNC 1421 performs functions suchas, but not limited to, load control, packet scheduling, handovercontrol, security functions, as well as controlling Mobile Station1401's access to the Core Network (CN) 1440.

The evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 1430 is aradio access network that provides wireless data communications forMobile Station 1401 and User Equipment 1402. E-UTRAN 1430 provideshigher data rates than traditional UMTS. It is part of the Long TermEvolution (LTE) upgrade for mobile networks and later releases meet therequirements of the International Mobile Telecommunications (IMT)Advanced and are commonly known as a 4G networks. E-UTRAN 1430 mayinclude of series of logical network components such as E-UTRAN Node B(eNB) 1431 and E-UTRAN Node B (eNB) 1432. E-UTRAN 1430 may contain oneor more eNBs. User Equipment 1402 may be any user device capable ofconnecting to E-UTRAN 1430 including, but not limited to, a personalcomputer, laptop, mobile device, wireless router, or other devicecapable of wireless connectivity to E-UTRAN 1430. The improvedperformance of the E-UTRAN 1430 relative to a typical UMTS networkallows for increased bandwidth, spectral efficiency, and functionalityincluding, but not limited to, voice, high-speed applications, largedata transfer and IPTV, while still allowing for full mobility.

An example embodiment of a mobile data and communication service thatmay be implemented in the PLMN architecture described in FIG. 8 is theEnhanced Data rates for GSM Evolution (EDGE). EDGE is an enhancement forGPRS networks that implements an improved signal modulation scheme knownas 8-PSK (Phase Shift Keying). By increasing network utilization, EDGEmay achieve up to three times faster data rates as compared to a typicalGPRS network. EDGE may be implemented on any GSM network capable ofhosting a GPRS network, making it an ideal upgrade over GPRS since itmay provide increased functionality of existing network resources.Evolved EDGE networks are becoming standardized in later releases of theradio telecommunication standards, which provide for even greaterefficiency and peak data rates of up to 1 Mbit/s, while still allowingimplementation on existing GPRS-capable network infrastructure.

Typically Mobile Station 1401 may communicate with any or all of BSS1410, RNS 1420, or E-UTRAN 1430. In a illustrative system, each of BSS1410, RNS 1420, and E-UTRAN 1430 may provide Mobile Station 1401 withaccess to Core Network 1440. The Core Network 1440 may include of aseries of devices that route data and communications between end users.Core Network 1440 may provide network service functions to users in theCircuit Switched (CS) domain, the Packet Switched (PS) domain or both.The CS domain refers to connections in which dedicated network resourcesare allocated at the time of connection establishment and then releasedwhen the connection is terminated. The PS domain refers tocommunications and data transfers that make use of autonomous groupingsof bits called packets. Each packet may be routed, manipulated,processed or handled independently of all other packets in the PS domainand does not require dedicated network resources.

The Circuit Switched—Media Gateway Function (CS-MGW) 1441 is part ofCore Network 1440, and interacts with Visitor Location Register (VLR)and Mobile-Services Switching Center (MSC) Server 1460 and Gateway MSCServer 1461 in order to facilitate Core Network 1440 resource control inthe CS domain. Functions of CS-MGW 1441 include, but are not limited to,media conversion, bearer control, payload processing and other mobilenetwork processing such as handover or anchoring. CS-MGW 1440 mayreceive connections to Mobile Station 1401 through BSS 1410, RNS 1420 orboth.

Serving GPRS Support Node (SGSN) 1442 stores subscriber data regardingMobile Station 1401 in order to facilitate network functionality. SGSN1442 may store subscription information such as, but not limited to, theInternational Mobile Subscriber Identity (IMSI), temporary identities,or Packet Data Protocol (PDP) addresses. SGSN 1442 may also storelocation information such as, but not limited to, the Gateway GPRSSupport Node (GGSN) 1444 address for each GGSN where an active PDPexists. GGSN 1444 may implement a location register function to storesubscriber data it receives from SGSN 1442 such as subscription orlocation information.

Serving Gateway (S-GW) 1443 is an interface which provides connectivitybetween E-UTRAN 1430 and Core Network 1440. Functions of S-GW 1443include, but are not limited to, packet routing, packet forwarding,transport level packet processing, event reporting to Policy andCharging Rules Function (PCRF) 1450, and mobility anchoring forinter-network mobility. PCRF 1450 uses information gathered from S-GW1443, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources and other networkadministration functions. Packet Data Network Gateway (PDN-GW) 1445 mayprovide user-to-services connectivity functionality including, but notlimited to, network-wide mobility anchoring, bearer session anchoringand control, and IP address allocation for PS domain connections.

Home Subscriber Server (HSS) 1463 is a database for user information,and stores subscription data regarding Mobile Station 1401 or UserEquipment 1402 for handling calls or data sessions. Networks may containone HSS 1463 or more if additional resources are required. Example datastored by HSS 1463 include, but is not limited to, user identification,numbering and addressing information, security information, or locationinformation. HSS 1463 may also provide call or session establishmentprocedures in both the PS and CS domains.

The VLR/MSC Server 1460 provides user location functionality. WhenMobile Station 1401 enters a new network location, it begins aregistration procedure. A MSC Server for that location transfers thelocation information to the VLR for the area. A VLR and MSC Server maybe located in the same computing environment, as is shown by VLR/MSCServer 1460, or alternatively may be located in separate computingenvironments. A VLR may contain, but is not limited to, user informationsuch as the IMSI, the Temporary Mobile Station Identity (TMSI), theLocal Mobile Station Identity (LMSI), the last known location of themobile station, or the SGSN where the mobile station was previouslyregistered. The MSC server may contain information such as, but notlimited to, procedures for Mobile Station 1401 registration orprocedures for handover of Mobile Station 1401 to a different section ofthe Core Network 1440. GMSC Server 1461 may serve as a connection toalternate GMSC Servers for other mobile stations in larger networks.

Equipment Identity Register (EIR) 1462 is a logical element which maystore the International Mobile Equipment Identities (IMEI) for MobileStation 1401. In a typical embodiment, user equipment may be classifiedas either “white listed” or “black listed” depending on its status inthe network. In one embodiment, if Mobile Station 1401 is stolen and putto use by an unauthorized user, it may be registered as “black listed”in EIR 1462, preventing its use on the network. Mobility ManagementEntity (MME) 1464 is a control node which may track Mobile Station 1401or User Equipment 1402 if the devices are idle. Additional functionalitymay include the ability of MME 1464 to contact an idle Mobile Station1401 or User Equipment 1402 if retransmission of a previous session isrequired.

While example embodiments of text message generation for emergencyservices as a backup to voice communications have been described inconnection with various computing devices/processors, the underlyingconcepts may be applied to any computing device, processor, or systemcapable of implementing text message generation for emergency servicesas a backup to voice communications. The various techniques describedherein can be implemented in connection with hardware or software or,where appropriate, with a combination of both. Thus, the methods andapparatuses of using and implementing text message generation foremergency services as a backup to voice communications may beimplemented, or certain aspects or portions thereof, can take the formof program code (i.e., instructions) embodied in tangible storage mediahaving a tangible physical structure. Examples of tangible storage mediainclude floppy diskettes, CD-ROMs, DVDs, hard drives, or any othertangible machine-readable storage medium (computer-readable storagemedium). Thus, a computer-readable storage medium is not a transientsignal per se. When the program code is loaded into and executed by amachine, such as a computer, the machine becomes an apparatus forimplementing text message generation for emergency services as a backupto voice communications. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile and non-volatile memory and/or storage elements), at least oneinput device, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and combined with hardwareimplementations.

The methods and apparatuses for using and implementing text messagegeneration for emergency services as a backup to voice communicationsalso may be practiced via communications embodied in the form of programcode that is transmitted over some transmission medium, such as overelectrical wiring or cabling, through fiber optics, or via any otherform of transmission, wherein, when the program code is received andloaded into and executed by a machine, such as an EPROM, a gate array, aprogrammable logic device (PLD), a client computer, or the like, themachine becomes an apparatus for implementing text message generationfor emergency services as a backup to voice communications. Whenimplemented on a general-purpose processor, the program code combineswith the processor to provide a unique apparatus that operates to invokethe functionality of text message generation for emergency services as abackup to voice communications.

While text message generation for emergency services as a backup tovoice communications has been described in connection with the variousembodiments of the various figures, it is to be understood that othersimilar embodiments can be used or modifications and additions can bemade to the described embodiments for implementing text messagegeneration for emergency services as a backup to voice communicationswithout deviating therefrom. For example, one skilled in the art willrecognize that text message generation for emergency services as abackup to voice communications as described in the present applicationmay apply to any environment, whether wired or wireless, and may beapplied to any number of such devices connected via a communicationsnetwork and interacting across the network. Therefore, text messagegeneration for emergency services as a backup to voice communicationsshould not be limited to any single embodiment, but rather should beconstrued in breadth and scope in accordance with the appended claims.

What is claimed:
 1. A method comprising: receiving an indication of anemergency voice call; receiving an indication of an emergency textmessage; generating an identifier indicating that the emergency voicecall and the emergency text message are correlated based on theemergency voice call and the emergency text message being generated by acommon source, the identifier comprising: an indication of the commonsource; and a correlation number; generating first signaling comprisingthe indication of the emergency voice call and the identifier;generating second signaling comprising the indication of the emergencytext message and the identifier; providing the first signaling via afirst communication network; and providing the second signaling via asecond communication network.
 2. The method of claim 1, wherein: thefirst network differs from the second network.
 3. The method of claim 1,wherein: the first network comprises circuitry for communicating a voicecall; and the second network comprises circuitry for communicating data.4. The method of claim 1, wherein: the indication of the emergency textmessage is indicative of being automatically generated upon dialing anumber for the emergency voice call.
 5. The method of claim 1, wherein:the second signaling comprises a data packet comprising the identifier.6. The method of claim 1, wherein: the second signaling comprises a IPdata packet comprising the identifier in a header of the IP data packet.7. The method of claim 1, wherein: an intended recipient of theemergency voice call is a public services answering position.
 8. Themethod of claim 1, wherein: the emergency text message comprises a anindication of sender of the emergency text message.
 9. The method ofclaim 1, wherein: the emergency text message comprises a an indicationof a location of a device from which the emergency text message wassent.
 10. The method of claim 1, wherein: the emergency text messagecomprises a text message resulting from a voice to text conversion. 11.A method comprising: receiving an indication of a voice call;determining that the voice call is an emergency voice call; upondetermining that the voice call is an emergency voice call,automatically generating an emergency text message; generating anidentifier indicating that the emergency voice call and the emergencytext message are correlated based on the emergency voice call and theemergency text message being generated by a common source, theidentifier comprising: an indication of the common source; and acorrelation number; generating first signaling comprising the indicationof the emergency voice call and the identifier; generating secondsignaling comprising the indication of the emergency text message andthe identifier; providing the first signaling via a first communicationnetwork; and providing the second signaling via a second communicationnetwork.
 12. The method of claim 11, wherein: the indication of theinitiation of the emergency voice call comprised dialed digits.
 13. Themethod of claim 11, wherein: the indication of the initiation of theemergency voice call comprised dialed digits comprising numbers 9, 1,and
 1. 14. The method of claim 11, wherein: an intended recipient of theemergency voice call is a public services answering position.
 15. Themethod of claim 11, wherein: the voice call is determined to be anemergency voice call based on a number dialed being a number of apredetermined list of numbers.
 16. The method of claim 11, wherein: theemergency text message comprises a predetermined text message.
 17. Themethod of claim 11, wherein: the emergency text message comprises a anindication of sender of the emergency text message.
 18. The method ofclaim 11, wherein: the emergency text message comprises a an indicationof a location of the device.
 19. The method of claim 11, wherein: theemergency text message comprises a text message resulting from a voiceto text conversion.
 20. A computer-readable storage medium comprisingexecutable instruction that when executed by a processor cause theprocessor to effectuating operations comprising: receiving an indicationof an emergency voice call; receiving an indication of an emergency textmessage; generating an identifier indicating that the emergency voicecall and the emergency text message are correlated based on theemergency voice call and the emergency text message being generated by acommon source, the identifier comprising: an indication of the commonsource; and a correlation number; generating first signaling comprisingthe indication of the emergency voice call and the identifier;generating second signaling comprising the indication of the emergencytext message and the identifier; providing the first signaling via afirst communication network; and providing the second signaling via asecond communication network.